SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 62751: Value Data in scoring model groups fails to score counterparty data and returns "ERROR: The VALUEDATA data set is missing the variable..."

DetailsHotfixAboutRate It

In SAS® Model Implementation Platform, the Value Data data objects support only KEY = INSTID, which can cause them to fail to score counterparty data. This failure occurs because counterparty data requires KEY = CPTYID. Note that the underlying SAS® High-Performance Risk functionality supports both KEY = INSTID and KEY = CPTYID. 

The issue occurs when you associate a Value Data object with your scoring model group through the user interface. Then, messages similar to the following are printed in the log:
Note: The name of the risk data object (ValData_Test) and the name of the value data dataset (valdat2) are specific to this example.

WARNING: There was a problem setting up the VALUEDATA data set MIPVAL.valdat2 for the VALUEDATA object 'ValData_Test'.
ERROR: The VALUEDATA data set is missing the variable 'InstID'.

To work around this issue, define the Value Data with the KEY = CPTYID risk data object for counterparty scoring in the risk environment in a pre-execution program. To circumvent the error shown above, use code that is similar to the following:

proc risk;
   env new=mipenv.risk_env inherit=(mimp_env.base_risk_env);
 
   marketdata value_data type=valuedata file=mipval.valdat2 key=CPTYID;
   valuedata ValData_Test data=value_data;
 
   setoptions NOBACKSAVE;
   env save;
run;

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Model Implementation PlatformWindows 7 Professional 32 bit3.13.29.4 TS1M59.4 TS1M5
Windows 7 Home Premium x643.13.29.4 TS1M59.4 TS1M5
Windows 7 Home Premium 32 bit3.13.29.4 TS1M59.4 TS1M5
Windows 7 Enterprise x643.13.29.4 TS1M59.4 TS1M5
Windows 7 Enterprise 32 bit3.13.29.4 TS1M59.4 TS1M5
Microsoft Windows Server 20163.13.29.4 TS1M59.4 TS1M5
Microsoft Windows Server 2012 Std3.13.29.4 TS1M59.4 TS1M5
Microsoft Windows Server 2012 R2 Std3.13.29.4 TS1M59.4 TS1M5
Microsoft Windows Server 2012 R2 Datacenter3.13.29.4 TS1M59.4 TS1M5
Microsoft Windows Server 2012 Datacenter3.13.29.4 TS1M59.4 TS1M5
Microsoft Windows Server 2008 for x643.13.29.4 TS1M59.4 TS1M5
Microsoft Windows Server 2008 R23.13.29.4 TS1M59.4 TS1M5
Microsoft Windows Server 20083.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 103.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 8.1 Pro x643.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 8.1 Pro 32-bit3.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 8.1 Enterprise x643.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 8.1 Enterprise 32-bit3.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 8 Pro x643.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 8 Pro 32-bit3.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 8 Enterprise x643.13.29.4 TS1M59.4 TS1M5
Microsoft Windows 8 Enterprise 32-bit3.13.29.4 TS1M59.4 TS1M5
Microsoft® Windows® for x643.13.29.4 TS1M59.4 TS1M5
Windows 7 Professional x643.13.29.4 TS1M59.4 TS1M5
Windows 7 Ultimate 32 bit3.13.29.4 TS1M59.4 TS1M5
Windows 7 Ultimate x643.13.29.4 TS1M59.4 TS1M5
Linux for x643.13.29.4 TS1M59.4 TS1M5
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.